User Acceptance Tests① consist of a set of test steps, which verify if specific requirements are working for the user.
If the customer and the supplier agree on the product, the software development is done. Legally. And practically.
Functional testing, on the other hand, tests specific requirements and specifications of the software. It lacks the user
component. A functional test could conclude that the software meets its specifications. However, it doesn’t verify if it
actually works for the user. The functional dimension is only one of many.
We did functional testing with client Mike on our mock-up prototype of interface(shown in User Interface). It all worked.
Then we interviewed 3 students in our course as user acceptance tests. We asked their feelings when using the app. All went
well except one thing. They told us the color of background picture made it difficult to see the words. It means although the
interface worked well in functional tests, it failed in user user acceptance tests. So we changed the background picture in our
latest prototype(shown in Prototype).
Reference
①http://usersnap.com/blog/types-user-acceptance-tests-frameworks/